You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs(mobile): Screens fork doc points at each archive's recorded source - #28293
docs/operations/mobile-screens-fork.md links the T3 Screens fork at tag t3-v5.0.0-t3.45. The app now ships react-native-screens-5.0.0-t3.48.tgz (#18492). So the link points at older source than the archive in apps/mobile/deps.
pingdotgg/react-native-screens now has a t3-v5.0.0-t3.48 tag at the archive's recorded commit, but no t3.46 or t3.47 tag. The t3.48 source and tag are on the fork named in that archive's t3-fork.json, as #18492's description links. The t3.45 archive also named a personal fork there, and pingdotgg/react-native-screens now has its t3-v5.0.0-t3.45 tag at the same commit. The link has been bumped by hand each time, once to a personal fork (#24206) and back (#24951).
Change
The link goes to the pingdotgg fork itself, with no version pinned.
The doc says t3-fork.json also records the source repository.
To reproduce an archive, check out the repository and commit that t3-fork.json records.
The doc then stays correct across Screens bumps, and nobody has to edit the link each time.
Scope and approval
This fixes a stale link in a maintainer doc, under the obvious-bug exception. It changes no code. The update steps still say to publish the tag to the fork. The missing t3.46 and t3.47 tags on pingdotgg/react-native-screens are for a maintainer to push. This PR doesn't change that process.
Verification
This is a maintainer doc, so no screen changes. I ran the checks below on main e63d80a (the newest main with green push CI), on this PR's head c472824, and on the head merged locally with that main (572350f65b, not pushed). All three ship the same t3.48 archive.
Before, on main e63d80a. The doc links tag t3.45, while the shipped archive is t3.48 and records a different repository:
After, on head c472824. The link pins no version, the doc sends readers to the repository and commit the archive records, and that commit resolves:
$ git rev-parse HEAD
c472824ecc1dc782fa9722581f8f515fceb74327
$ sed -n '3,13p' docs/operations/mobile-screens-fork.md
The mobile v5 stack uses a committed tarball from the
[T3 Screens fork](https://github.com/pingdotgg/react-native-screens).
The fork owns the integration changes; the app does not patch this package.
Each archive includes compiled JavaScript, declarations, native source and
`t3-fork.json` recording its source repository, version, source commit and
upstream base.
To reproduce an archive, use Node 24 and the repository's pinned Yarn from a
clean checkout of the source repository and commit recorded in its
`t3-fork.json`:
$ git ls-remote https://github.com/PixPMusic/react-native-screens | grep 6ce484b346dd0d51e84566696a1b1a1af4dc6225
6ce484b346dd0d51e84566696a1b1a1af4dc6225 refs/heads/fix/android-routed-sheet-centering
6ce484b346dd0d51e84566696a1b1a1af4dc6225 refs/tags/t3-v5.0.0-t3.48^{}
$ curl -s -o /dev/null -w '%{http_code}\n' https://github.com/PixPMusic/react-native-screens/commit/6ce484b346dd0d51e84566696a1b1a1af4dc6225
200
$ curl -s -o /dev/null -w '%{http_code}\n' https://github.com/pingdotgg/react-native-screens
200
Head merged with main e63d80a (local, not pushed):
$ git rev-parse HEAD
572350f65b3ad8623f7ca506fd35ec9b8b6b41b1
$ git log -1 --format=%P HEAD
e63d80a06526ad624c92cb784152d034ed5ed6de c472824ecc1dc782fa9722581f8f515fceb74327
$ sed -n '3,13p' docs/operations/mobile-screens-fork.md
The mobile v5 stack uses a committed tarball from the
[T3 Screens fork](https://github.com/pingdotgg/react-native-screens).
The fork owns the integration changes; the app does not patch this package.
Each archive includes compiled JavaScript, declarations, native source and
`t3-fork.json` recording its source repository, version, source commit and
upstream base.
To reproduce an archive, use Node 24 and the repository's pinned Yarn from a
clean checkout of the source repository and commit recorded in its
`t3-fork.json`:
$ tar -xzOf apps/mobile/deps/react-native-screens-5.0.0-t3.48.tgz package/t3-fork.json
{
"repository": "https://github.com/PixPMusic/react-native-screens",
"commit": "6ce484b346dd0d51e84566696a1b1a1af4dc6225",
"upstreamCommit": "72f38a66c188bdebee7a7798c9b72a121b7a8451",
"version": "5.0.0-t3.48"
}
$ git ls-remote https://github.com/PixPMusic/react-native-screens | grep 6ce484b346dd0d51e84566696a1b1a1af4dc6225
6ce484b346dd0d51e84566696a1b1a1af4dc6225 refs/heads/fix/android-routed-sheet-centering
6ce484b346dd0d51e84566696a1b1a1af4dc6225 refs/tags/t3-v5.0.0-t3.48^{}
$ curl -s -o /dev/null -w '%{http_code}\n' https://github.com/PixPMusic/react-native-screens/commit/6ce484b346dd0d51e84566696a1b1a1af4dc6225
200
#18433 by juliusmarminge pointed this doc at the pingdotgg fork, and this keeps that. #18492 by PixPMusic shipped t3.48. I found no open PR that touches this file.
Generated with Claude Opus 5.5 and GPT-6.1 Sol in T3 Code Nightly
The doc linked the pingdotgg fork's t3-v5.0.0-t3.45 tag while the app ships 5.0.0-t3.48, whose source and tag live on the contributor fork named in its t3-fork.json. Link the fork itself and send readers to the repository and commit that t3-fork.json records, so the doc stays true across Screens bumps.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Macroscope's review found this PR approvable — The documentation now directs archive reproduction to the source repository and commit recorded in each archive instead of a fixed fork tag. No runtime behavior, product defaults, or diagnostic suppressions change.
You can add or adjust custom eligibility rules. Learn more.
No actionable comments were generated in the recent review.
Walkthrough
The Mobile Screens fork documentation now links to the repository, describes the source repository in archive metadata, and instructs readers to reproduce from the source repository and commit recorded in t3-fork.json.
Changes: Mobile Screens fork documentation
Layer / File(s)
Summary
Archive source and reproduction guidance docs/operations/mobile-screens-fork.md
The fork link points to the repository. Archive metadata includes the source repository. Reproduction instructions use a clean checkout of the source repository and commit recorded in t3-fork.json.
The documentation change has no identified merge-blocking issue.
Pre-merge checks: 4
Check name
Status
Explanation
Title check
The title clearly and concisely describes the documentation change: it points the Screens fork documentation to each archive’s recorded source.
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Description check
The description follows the repository template. It has Problem, Change, Scope and approval, and Verification sections. The problem is clear: the doc links tag t3-v5.0.0-t3.45, but the shipped archive…
Full details: Description check
Explanation
The description follows the repository template. It has Problem, Change, Scope and approval, and Verification sections. The problem is clear: the doc links tag t3-v5.0.0-t3.45, but the shipped archive is t3.48 and records a different source repository. The change is also clear: the link now points to the pingdotgg fork with no pinned version, and reproduction steps now use the repository and commit recorded in t3-fork.json. The scope section claims the obvious-bug exception and explains why it applies, since the change is a stale doc link with no code changes. Verification gives concrete commands and observed outputs on main, on the PR head, and on the merged tree, and it states what was not checked (no archive rebuild). The template's agent-attribution line is present at the end. Minor gaps: the verification section is long, and the description does not restate the CONTRIBUTING.md reference, but these are non-critical.
Finishing Touches
Generate unit tests (beta)
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
size:XS0-9 changed lines (additions + deletions).vouch:unvouchedPR author is not yet trusted in the VOUCHED list.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
github-actions
Bot
added
vouch:unvouched
![macroscopeapp[bot]](https://avatars.githubusercontent.com/in/900172?s=60&v=4){kind=small}
Problem
docs/operations/mobile-screens-fork.mdlinks the T3 Screens fork at tagt3-v5.0.0-t3.45. The app now shipsreact-native-screens-5.0.0-t3.48.tgz(#18492). So the link points at older source than the archive inapps/mobile/deps.pingdotgg/react-native-screens now has a
t3-v5.0.0-t3.48tag at the archive's recorded commit, but not3.46ort3.47tag. The t3.48 source and tag are on the fork named in that archive'st3-fork.json, as #18492's description links. The t3.45 archive also named a personal fork there, and pingdotgg/react-native-screens now has itst3-v5.0.0-t3.45tag at the same commit. The link has been bumped by hand each time, once to a personal fork (#24206) and back (#24951).Change
t3-fork.jsonalso records the source repository.t3-fork.jsonrecords.The doc then stays correct across Screens bumps, and nobody has to edit the link each time.
Scope and approval
This fixes a stale link in a maintainer doc, under the obvious-bug exception. It changes no code. The update steps still say to publish the tag to the fork. The missing
t3.46andt3.47tags on pingdotgg/react-native-screens are for a maintainer to push. This PR doesn't change that process.Verification
This is a maintainer doc, so no screen changes. I ran the checks below on main e63d80a (the newest main with green push CI), on this PR's head c472824, and on the head merged locally with that main (572350f65b, not pushed). All three ship the same t3.48 archive.
Before, on main e63d80a. The doc links tag t3.45, while the shipped archive is t3.48 and records a different repository:
After, on head c472824. The link pins no version, the doc sends readers to the repository and commit the archive records, and that commit resolves:
Full tag list on main, and the merged tree
Main e63d80a:
Head merged with main e63d80a (local, not pushed):
CI's Check job passes on c472824.
Not checked:
Prior PRs
#18433 by juliusmarminge pointed this doc at the pingdotgg fork, and this keeps that. #18492 by PixPMusic shipped t3.48. I found no open PR that touches this file.
Generated with Claude Opus 5.5 and GPT-6.1 Sol in T3 Code Nightly